|
|
 |
|
|
|
|
5. Explain the nature of the form controller in subsystem-to-subsystem communications. |
|
|
|
|
|
|
|
|
Although it is certainly wise from a code reuse standpoint to not allow forms to directly communicate with the Database Access Subsystem, form controllers at times need to communicate with it. In fact, form controller classes aren't monopolized exclusively by the Graphical User Interface Subsystem in every situation. Sometimes a controller class can be the communication hub between the form business rules and the Database Access Subsystem. This is helpful when you're moving data in and out of a database, one record at a time, and no business rule processing occurs. Typical applications that might face this scenario include pure data entry applications in which the user is keying in information on a client machine, and that information is to be processed later by some server subsystem independent of the client. |
|
|
|
|
|
|
|
|
1. Why is it strongly advisable to approach all your Visual Basic development efforts with the utmost organization and methodology? |
|
|
|
|
|
|
|
|
You can usually handle only seven (plus or minus two) points of complexity. |
|
|
|
|
|
|
|
|
2. What factor increases the chances of successfully delivering a product written in Visual Basic? |
|
|
|
|
|
|
|
|
A factor that will increase the chances of successfully delivering a product written in Visual Basic is to have access to a Visual Basic developer who has experience in the best features of Visual Basic, including its object-oriented programming features. Having a good library of classes and components is also helpful. |
|
|
|
|
|
|
|
|
3. What are the important factors to consider in managing a Visual Basic project successfully? |
|
|
|
|
|
|
|
|
Give developers inexperienced with the powerful, overwhelming new features in Visual Basic the right resources to help them succeed, including acquiring an outside mentor if necessary. |
|
|
|
|
|
|
|
|
Track and maintain domain terminology so that developers are not later side-tracked on ambiguity in terms users use. |
|
|
|
|
|
|
|
|
Plan for the one- to three-month learning curve when hiring new developers on a fairly large project. (For smaller projects, the learning curve is typically shorter.) |
|
|
|
|
|
|
|
|
When reengineering an undocumented legacy system into a Visual Basic application, be sure to allow time to help users separate (within reason) the navigation of windows from the actual tasks they are trying to accomplish. |
|
|
|
|
|